-- Network Working Group M. Rose
-- Request for Comments: 1227 Performance Systems International, Inc.
-- May 1991-- SNMP MUX Protocol and MIBSMUX-MIB DEFINITIONS::=BEGINIMPORTSenterprises
FROM RFC1155-SMI
OBJECT-TYPEFROM RFC1212;unix OBJECTIDENTIFIER::={ enterprises 4}smux OBJECTIDENTIFIER::={ unix 4}smuxPeerTable OBJECT-TYPESYNTAXSEQUENCEOF SmuxPeerEntry
ACCESSnot-accessible
STATUSmandatoryDESCRIPTION"The SMUX peer table."::={ smux 1}smuxPeerEntry OBJECT-TYPESYNTAX SmuxPeerEntry
ACCESSnot-accessibleSTATUSmandatoryDESCRIPTION"An entry in the SMUX peer table."INDEX{ smuxPindex }::={ smuxPeerTable 1}
SmuxPeerEntry ::=SEQUENCE{
smuxPindex
INTEGER,
smuxPidentity
OBJECTIDENTIFIER,
smuxPdescription
DisplayString,
smuxPstatus
INTEGER}
smuxPindex OBJECT-TYPESYNTAXINTEGERACCESSread-onlySTATUSmandatoryDESCRIPTION"An index which uniquely identifies a SMUX peer."::={ smuxPeerEntry 1}smuxPidentity OBJECT-TYPESYNTAXOBJECTIDENTIFIERACCESSread-onlySTATUSmandatoryDESCRIPTION"The authoritative designation for a SMUX peer."::={ smuxPeerEntry 2}smuxPdescription OBJECT-TYPESYNTAXDisplayString(SIZE(0..255))
ACCESSread-onlySTATUSmandatoryDESCRIPTION"A human-readable description of a SMUX peer."::={ smuxPeerEntry 3}smuxPstatus OBJECT-TYPESYNTAXINTEGER{ valid(1), invalid(2), connecting(3)}ACCESSread-writeSTATUSmandatoryDESCRIPTION"The type of SMUX peer.
Setting this object to the value invalid(2) has
the effect of invaliding the corresponding entry
in the smuxPeerTable. It is an implementation-
specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly,
management stations must be prepared to receive
tabular information from agents that correspond to
entries not currently in use. Proper
interpretation of such entries requires
examination of the relative smuxPstatus object."::={ smuxPeerEntry 4}smuxTreeTable OBJECT-TYPESYNTAXSEQUENCEOF SmuxTreeEntry
ACCESSnot-accessibleSTATUSmandatoryDESCRIPTION"The SMUX tree table."::={ smux 2}smuxTreeEntry OBJECT-TYPESYNTAX SmuxTreeEntry
ACCESSnot-accessibleSTATUSmandatoryDESCRIPTION"An entry in the SMUX tree table."INDEX{ smuxTsubtree, smuxTpriority }
::={ smuxTreeTable 1}
SmuxTreeEntry ::=SEQUENCE{
smuxTsubtree
OBJECTIDENTIFIER,
smuxTpriority
INTEGER,
smuxTindex
INTEGER,
smuxTstatus
INTEGER}smuxTsubtree OBJECT-TYPESYNTAXOBJECTIDENTIFIERACCESSread-onlySTATUSmandatoryDESCRIPTION"The MIB subtree being exported by a SMUX peer."::={ smuxTreeEntry 1}smuxTpriority OBJECT-TYPESYNTAXINTEGER(0..'07fffffff'h)
ACCESSread-onlySTATUSmandatoryDESCRIPTION"The SMUX peer's priority when exporting the MIB
subtree."::={ smuxTreeEntry 2}smuxTindex OBJECT-TYPESYNTAXINTEGERACCESSread-onlySTATUSmandatoryDESCRIPTION"The SMUX peer's identity."::={ smuxTreeEntry 3}smuxTstatus OBJECT-TYPESYNTAXINTEGER{ valid(1), invalid(2)}ACCESSread-write
STATUSmandatoryDESCRIPTION"The type of SMUX tree.
Setting this object to the value invalid(2) has
the effect of invaliding the corresponding entry
in the smuxTreeTable. It is an implementation-
specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly,
management stations must be prepared to receive
tabular information from agents that correspond to
entries not currently in use. Proper
interpretation of such entries requires
examination of the relative smuxTstatus object."::={ smuxTreeEntry 4}END